Congratulations! Your application's GC activity is healthy.
| Generation | Allocated | Peak |
|---|---|---|
| Young Generation | 8.57 gb | 8.21 gb |
| Old Generation | 5.13 gb | 6.2 gb |
| Total | 13.7 gb | 12.3 gb |
(Important section of the report. To learn more about KPIs, click here)
1 Throughput : 99.946%
2 Latency:
| Avg Pause GC Time | 176 ms |
|---|---|
| Max Pause GC Time | 1 sec 230 ms |
| Duration (secs) | No. of GCs | Percentage |
|---|---|---|
| 0 - 1 | 6005 | 99.9% |
| 1 - 2 | 6 | 100.0% |
(All graphs are zoomable)
| Young GC | Mixed | Concurrent Mark | initial-mark | Remark | Cleanup | Total | |
|---|---|---|---|---|---|---|---|
| Count | 5989 | 7 | 6 | 6 | 6 | 6 | 6020 |
| Total GC Time | 17 min 36 sec 906 ms | 1 sec 240 ms | 1 sec 138 ms | 930 ms | 810 ms | 60 ms | 17 min 41 sec 84 ms |
| Avg GC Time | 176 ms | 177 ms | 190 ms | 155 ms | 135 ms | 10 ms | 176 ms |
| Avg Time std dev | 193 ms | 56 ms | 339 ms | 174 ms | 257 ms | 10 ms | 193 ms |
| Min/Max Time | 0 / 1 sec 230 ms | 0 / 260 ms | 0 / 943 ms | 0 / 460 ms | 0 / 710 ms | 0 / 30 ms | 0 / 1 sec 230 ms |
| Avg Interval Time | 5 min 29 sec 828 ms | 10 sec 71 ms | 108 hrs 57 min 13 sec | 108 hrs 57 min 13 sec | 108 hrs 57 min 13 sec | 108 hrs 57 min 13 sec | 27 min 12 sec 814 ms |
| Total Time | 17 min 39 sec 946 ms |
|---|---|
| Avg Time | 176 ms |
| Std Dev Time | 193 ms |
| Min Time | 0 |
| Max Time | 1 sec 230 ms |
| Total Time | 1 sec 138 ms |
|---|---|
| Avg Time | 190 ms |
| Std Dev Time | 339 ms |
| Min Time | 1 ms |
| Max Time | 943 ms |
(These are perfect micro-metrics to include in your performance reports)
| Total created bytes | 18.25 tb |
|---|---|
| Total promoted bytes | 24.67 gb |
| Avg creation rate | 9.68 mb/sec |
| Avg promotion rate | 13 kb/sec |
No major memory leaks.
(Note: there are 8 flavours of OutOfMemoryErrors. With GC Logs you can diagnose only 5 flavours of them(Java heap space, GC overhead limit exceeded, Requested array size exceeds VM limit, Permgen space, Metaspace). So in other words, your application could be still suffering from memory leaks, but need other tools to diagnose them, not just GC Logs.)
None.
None.
(To learn more about SafePoint duration, click here)
Not Reported in the log.
(What events caused the GCs, how much time it consumed?)
| Cause | Count | Avg Time | Max Time | Total Time | Time % |
|---|---|---|---|---|---|
| G1 Evacuation Pause | 5890 | 176 ms | 1 sec 235 ms | 17 min 15 sec 544 ms | 97.59% |
| GCLocker Initiated GC | 108 | 205 ms | 947 ms | 22 sec 95 ms | 2.08% |
| Others | 18 | n/a | n/a | 3 sec 303 ms | 0.31% |
| Metadata GC Threshold | 4 | 36 ms | 50 ms | 142 ms | 0.01% |
| Total | 6020 | n/a | n/a | 17 min 41 sec 84 ms | 99.99% |
Not reported in the log.
-XX:CompileCommand=exclude,humanclick/pserv/run/POP3$MessageProcessor,process -XX:ErrorFile=:/liveperson/data/server_denver/logs/hs_err_pid%p.log -XX:InitialHeapSize=14680064000 -XX:+ManagementServer -XX:MaxHeapSize=14680064000 -XX:-OmitStackTraceInFastThrow -XX:+PrintConcurrentLocks -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+TraceClassLoading -XX:+TraceClassUnloading -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseG1GC
(Best practises/tools)
Please share your feedback. |
|||||
|
|
|||||
Thanks for your valuable Feedback!Your comment has been posted in the User Reviews page. |
|||||